-
Notifications
You must be signed in to change notification settings - Fork 273
Bug fixes to linking and C/C++ conversion #729
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
None of the ansi-c/gcc_builtin_headers_* is aligned with the coding standard - I'd thus hope the linter failure can be ignored. |
ff3a128
to
5df6af4
Compare
typecheck_expr(size_expr); | ||
simplify(size_expr, *this); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is that needed for?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's quite a while since I built that patch, but I suspect that is necessary to make some of the C++ regression tests pass. Also it is the same that the C front-end does.
This shouldn't get merged before #876 is merged. |
1 similar comment
This shouldn't get merged before #876 is merged. |
Needs a rebase, but is then ready to go |
Compilation using goto-cc used to be very noisy. Added source location information to make messages more comprehensible.
Non-symbol types may have been updated during linking; those updates had not been propagated to initializers or goto programs.
This is undocumented, but available as of GCC > 4.4: gcc-mirror/gcc@f0d0d84
@kroening Thanks, rebase done. |
This reverts commit a40fc8b.
constructors/destructors are a GCC extension, and their return type must be void as checked earlier. As the type is then replaced by ID_constructor/ID_destructor, and checks on the return type must consider this case.
We cannot arbitrarily convert strings to unicode representation as this would affect their size. Instead, only the unicode portion of a non-wide string must be encoded. As part of this work the code duplication unescape_string/unescape_wide_string is resolved. A new regression test confirms that the previous implementation was broken (and is now fixed).
No description provided.